home *** CD-ROM | disk | FTP | other *** search
- Path: soap.news.pipex.net!pipex!usenet
- From: m.hendry@dial.pipex.com (Mathew Hendry)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: Sysihack
- Date: Fri, 1 Mar 96 19:58:05
- Organization: Private node.
- Distribution: world
- Message-ID: <19960301.500CF0.119C2@am148.du.pipex.com>
- References: <182.6634T228T703@sasknet.sk.ca>
- NNTP-Posting-Host: am148.du.pipex.com
- X-Newsreader: TIN [AMIGA 1.3 950726BETA PL0]
-
- Brian Veroba (verob@sasknet.sk.ca) wrote:
- : I tried to use the program Sysihack, but no matter where I put it in
- : the Startup-Sequence it comes up with a requester that says it must be
- : started before IPrefs.
- :
- : Any ideas?
-
- SysIHack will come up with that error if _any_ program (not just IPrefs) has
- caused the Workbench screen to be opened. This will happen if a program
- produces output in the shell window - stop it from doing so by adding
- >NIL: after the "offending" command name, which redirects its output into
- the void.
-
- e.g. since C:SetPatch produces output, replace it with:
-
- C:SetPatch >NIL:
-
- However, even with this precaution, SysIHack sometimes fails unpredictably. In
- that case, you'll have to fiddle around with the _order_ of the executed
- commands as well - and note that commands _after_ SysIHack can screw things up
- too, because SysIHack detaches from its parent shell, and the patches take
- some time to be put in place.
-
- Just play around with it - it'll work eventually ;)
-
- -- Mat.
-